Received: from e55.webcom.com (e55.webcom.com [206.2.192.66]) by keeper.albany.net (8.7.5/8.7.5-MZ) with ESMTP id EAA11392 for <DWARNER@ALBANY.NET>; Sat, 27 Apr 1996 04:42:31 -0400 (EDT)
Received: from localhost by e55.webcom.com with SMTP
(1.37.109.15/16.2) id AA222264526; Sat, 27 Apr 1996 01:42:06 -0700
Date: Sat, 27 Apr 1996 01:42:06 -0700
Errors-To: dwarner@ALBANY.NET
Message-Id: <1261@scribendum.win-uk.net>
Errors-To: dwarner@ALBANY.NET
Reply-To: lightwave@garcia.com
Originator: lightwave@garcia.com
Sender: lightwave@garcia.com
Precedence: bulk
From: Stephen Benson <stephenb@scribendum.win-uk.net>
To: Multiple recipients of list <lightwave@garcia.com>
Subject: Re: A bone to pick...
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Status: RO
X-Status:
>>bones so far. This would have been a whole lot easier if I could have
>>simply created one chain of bones, then cloned it twelve times with a
>>linear offset.
>
>Bones were not meant to clone.. use the '+' hotkey instead to add a
>bone, or more commonly, the '=' key to add a Child Bone.
But that doesn't necessarily put them where you want, nor is it
quick... I did a dancing rug (don't ask) where I needed a lot of
control, being able to clone a certain set of bones (size, rest
length etc) a couple of times with an offset would have been
invaluable. The scene file hacking seems to be the only answer.